The mirror rule is a one-way synchronization method. When using a mirror rule, SureSync will copy, add, and delete files so that destination path(s) are identical to the source.

Any files which are added to a destination will be deleted if those files do not exist on the source. Any files modified on the destination will be replaced with the file copies from the source. A mirror forces the destination directories to appear, in every way, identical to the source. Changes must be made on the source to be retained.

Please note:

 

• A mirror rule is one of two one-way rules which will delete files. A move rule will also delete files.
• When running a mirror, if a file has changes on multiple roots, SureSync will automatically replace the destination(s) files with a copy of the source file. There will be no warning. Any changes made only to a destination path will be overwritten the next time the synchronization is run. Any change you want to have remain must be made on the source.

Possible Scenarios

Distribute a master set of documents

If you have a set of documents that you must ensure are the same in all offices, a mirror rule is ideal. For example, if your company has a set of important template files, the mirror rule will force all offices to have the same versions of the template. Any modifications made to the destination versions of the templates would be replaced with the source templates on the next run of the synchronization.

Publish web content from a staging server

Frequently, web developers will develop on a staging server. This allows the developers to test the web pages before going live. SureSync can be used with a mirror rule to publish the web content from the staging server. This ensures that the live server has the most recent version of files from the staging server. This eliminates all manual copy work involved in publishing the live site.

Summary Chart

The summary chart will give you a breakdown of how the Mirror rule functions when different events occur.